!PCARes is a resource for the PCA system.

You should place it in a directory where it will be 'seen' by the filer
before any PCA applications are seen or run. (I suggest !Boot.Choices.Tasks)

!PCARes defines a system path PCA$Path, and the PCA support module
should be RMEnsured from this path in the !Boot and !Run files of any
PCA using applications (the module should already be running if PCARes
is in Choices.Tasks and this is the 'best case'). If it isn't
running, it should be started with 'run PCA:KickPCA' so that it
initialises correctly as a desktop task under both NCOS and RISC OS.

Like this:

If "<PCA$Path>"="" Then Error Please locate PCA resources.

rmensure PCASupport 0.32 run PCA:KickPCA
rmensure PCASupport 0.32 Error Version 0.32 or later of the PCA support module is required.

Applications should NOT include a copy of the PCA module. Instead,
provide a skeleton copy of !PCARes so that there is only ever one copy
of the pca module on the users system at one time.

!PCARes also provides two pseudo *Commands for the use of programmers
and techies:

*BootPCA <bootfile>

This runs a simple scripting program which executes the script file
given (if it exists) in !PCARes.AppBoot. The format of the script
language is very simple and you should be able to grasp it from looking
at the examples provided.

The task handles of any applications started as a result of a *BootPCA will
be recorded in a file in Wimp$ScrapDir ready for *QuitPCA

*QuitPCA <bootfile>

This searches for a file of the same name inside the pca scrap directory
and sends quit messages to the task handles given in this file.
It plays it safe, checking that the task name of a given handle
is correct before telling it to quit.


The purpose of these commands is to allow a component-ware application
or a suitably aware user to auto start a set of PCA tools and easily
quit them later.
